Verifying resource functionality before use by a grid job submitted to a grid environment

ABSTRACT

When a new resource is allocated to a particular execution environment within a grid environment managed by a grid management system, then a grid verification service automatically selects and runs at least one functionality test on the new resource as controlled by the grid management system. Responsive to a result of the functionality test, the grid verification system verifies whether the result meets an expected result before enabling routing of the grid job to the new resource, such that the functionality of the new resource is automatically verified before access to the new resource is allowed to maintain quality of service in processing grid jobs.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to the following co-pendingapplications:

(1) U.S. patent application Ser. No. 11/031,490, filed Jan. 6, 2005;

(2) U.S. patent application Ser. No. 11/031,541, filed Jan. 6, 2005;

(3) U.S. patent application Ser. No. 11/031,543, filed Jan. 6, 2005.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to improved grid computing and,in particular, to automated verification of resource functionality forresources within a grid environment. Still more particularly, thepresent invention relates to verifying grid resource functionalitybefore enabling routing of a grid job submitted to the grid environmentto the resources, such that the functionality of resources handling gridjobs is ensured.

2. Description of the Related Art

Ever since the first connection was made between two computer systems,new ways of transferring data, resources, and other information betweentwo computer systems via a connection continue to develop. In typicalnetwork architectures, when two computer systems are exchanging data viaa connection, one of the computer systems is considered a client sendingrequests and the other is considered a server processing the requestsand returning results. In an effort to increase the speed at whichrequests are handled, server systems continue to expand in size andspeed. Further, in an effort to handle peak periods when multiplerequests are arriving every second, server systems are often joinedtogether as a group and requests are distributed among the groupedservers. Multiple methods of grouping servers have developed such asclustering, multi-system shared data (sysplex) environments, andenterprise systems. With a cluster of servers, one server is typicallydesignated to manage distribution of incoming requests and outgoingresponses. The other servers typically operate in parallel to handle thedistributed requests from clients. Thus, one of multiple servers in acluster may service a client request without the client detecting that acluster of servers is processing the request.

Typically, servers or groups of servers operate on a particular networkplatform, such as Unix or some variation of Unix, and provide a hostingenvironment for running applications. Each network platform may providefunctions ranging from database integration, clustering services, andsecurity to workload management and problem determination. Each networkplatform typically offers different implementations, semantic behaviors,and application programming interfaces (APIs).

Merely grouping servers together to expand processing power, however, isa limited method of improving efficiency of response times in a network.Thus, increasingly, within a company network, rather than just groupingservers, servers and groups of server systems are organized asdistributed resources. There is an increased effort to collaborate,share data, share cycles, and improve other modes of interaction amongservers within a company network and outside the company network.Further, there is an increased effort to outsource nonessential elementsfrom one company network to that of a service provider network.Moreover, there is a movement to coordinate resource sharing betweenresources that are not subject to the same management system, but stilladdress issues of security, policy, payment, and membership. Forexample, resources on an individual's desktop are not typically subjectto the same management system as resources of a company server cluster.Even different administrative groups within a company network mayimplement distinct management systems.

The problems with decentralizing the resources available from serversand other computing systems operating on different network platforms,located in different regions, with different security protocols and eachcontrolled by a different management system, has led to the developmentof Grid technologies using open standards for operating a gridenvironment. Grid environments support the sharing and coordinated useof diverse resources in dynamic, distributed, virtual organizations. Avirtual organization is created within a grid environment when aselection of resources, from geographically distributed systems operatedby different organizations with differing policies and managementsystems, is organized to handle a job request.

While clusters or other groups of servers can be grouped within a gridenvironment, Grid technologies do not solve all the problems associatedwith ensuring quality of service and performance where groups ofresources are managed by different management systems with differentstandards are handling grid jobs. In particular, an attribute andbenefit of grid technology is that resources are moved around intodifferent virtual organizations, also referred to as executionenvironments, to optimize available resources. Clients submitting jobsto any computing system expect that the resources provided to handle agrid job are functional. A problem in the grid environment, however, isthat with each resource reallocation to a new execution environment,however, the functionality of the resource is no longer verified. Forexample, when a network adapter is allocated in a new executionenvironment, connectivity with the network adapter is no longer verifiedunless a system administrator runs a test to ensure the connectivity ofthe network adapter. As the number of resources and resourcereallocations increases in a grid environment, using a systemadministrator to manually select and run tests for each resource willdegrade performance.

In view of the foregoing, there is a need for a computer-implementedmethod, system, and program for detecting new resources in an executionenvironment, testing each resource for functionality, and verifying thefunctionality of a resource, before routing a grid job to that resource,to assure quality of service of each job submitted to a gridenvironment.

SUMMARY OF THE INVENTION

In view of the foregoing, the invention provides for grid computing andin particular automated verification of resource functionality forresources within a grid environment. The invention relates to verifyingresources within an execution environment before enabling routing of agrid job submitted to the grid environment to the resources within theexecution environment, such that the functionality of resources handlinggrid jobs is ensured.

When a new resource is allocated to a particular execution environmentwithin a grid environment managed by a grid management system, then agrid verification service automatically selects and runs at least onefunctionality test on the new resource as controlled by the gridmanagement system. Responsive to a result of the functionality test, thegrid verification system verifies whether the result meets an expectedresult before enabling routing of the grid job to the new resource, suchthat the functionality of the new resource is automatically verifiedbefore access to the new resource is allowed to maintain quality ofservice in processing grid jobs.

The grid management system may detect that a new resource is allocatedto a particular execution environment when the new resource is added toan existing execution environment of resources previously tested forfunctionality. In addition, grid management system may detect that a newresource is allocated to a particular execution environment that isnewly built, and thus all the resources in the execution environmentneed to be tested for functionality. Further, the grid management systemdetects that a new resource is allocated to a particular execution toreplace a defective resource in the execution environment.

In running at least one functionality test on the new resource, testsare selected according to type of resource and further specifiedaccording to class of resource or resource brand. One type offunctionality test directs a test job to the new resource from the gridmanagement system and the test result for the test job is collected.Another type of functionality test calls a diagnostic tool enabled tolocally test the new resource and a log file indicating the test resultsis received.

If an error condition is detected in the result, the grid verificationservice attempts to resolve the error. If the error is resolved, thenthe grid verification service verifies the functionality of the newresource. If the error is not resolved, then the grid verificationservice identifies the error and the grid management system attempts toreplace the resource.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed aspect of the invention are set forth in theappended claims. The invention itself however, as well as a preferredmode of use, further objects and advantages thereof, will best beunderstood by reference to the following detailed description of anillustrative embodiment when read in conjunction with the accompanyingdrawings, wherein:

FIG. 1 depicts one embodiment of a computer system which may beimplemented in a grid environment and in which the present invention maybe implemented;

FIG. 2 is block diagram illustrating one embodiment of the general typesof components within a grid environment;

FIG. 3 is a block diagram depicting one example of an architecture thatmay be implemented in a grid environment;

FIG. 4 is a block diagram depicting an instance of a grid managementsystem managing multiple execution environments within a gridenvironment in accordance with the method, system, and program of thepresent invention; and

FIG. 5 is a block diagram depicting a block diagram of a grid managementsystem for managing a grid environment in accordance with the method,system, and program of the present invention;

FIG. 6 is a block diagram depicting a block diagram of examples ofcomponents of a grid verification service in accordance with the method,system, and program of the present invention;

FIG. 7 is a block diagram depicting an illustrative example of entriesin a test availability table in accordance with the method, system, andprogram of the present invention;

FIG. 8 is a high level logic flowchart of a process and program forcontrolling grid job routing to verified resources within an executionenvironment for the grid job in accordance with the method, system, andprogram of the present invention; and

FIG. 9 is a high level logic flowchart of a process and program forcontrolling resource verification for resources added to an executionenvironment for a grid job prior to grid job submission to the resourcesin accordance with the method, system, and program of the presentinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring now to the drawings and in particular to FIG. 1, there isdepicted one embodiment of a computer system which may be implemented ina grid environment and in which the present invention may beimplemented. As will be further described, the grid environment includesmultiple computer systems managed to provide resources. Additionally, aswill be further described, the present invention may be executed in avariety of computer systems, including a variety of computing systems,mobile systems, and electronic devices operating under a number ofdifferent operating systems managed within a grid environment.

In one embodiment, computer system 100 includes a bus 122 or otherdevice for communicating information within computer system 100, and atleast one processing device such as processor 112, coupled to bus 122for processing information. Bus 122 may include low-latency and higherlatency paths connected by bridges and adapters and controlled withincomputer system 100 by multiple bus controllers. When implemented as aserver system, computer system 100 typically includes multipleprocessors designed to improve network servicing power.

Processor 112 may be a general-purpose processor such as IBM's PowerPC™processor that, during normal operation, processes data under thecontrol of operating system and application software accessible from adynamic storage device such as random access memory (RAM) 114 and astatic storage device such as Read Only Memory (ROM) 116. The operatingsystem may provide a graphical user interface (GUI) to the user. In oneembodiment, application software contains machine executableinstructions that when executed on processor 112 carry out theoperations depicted in the flowcharts of FIGS. 8, 9, and otheroperations described herein. Alternatively, the steps of the presentinvention might be performed by specific hardware components thatcontain hardwired logic for performing the steps, or by any combinationof programmed computer components and custom hardware components.

The present invention may be provided as a computer program product,included on a machine-readable medium having stored thereon the machineexecutable instructions used to program computer system 100 to perform aprocess according to the present invention. The term “machine-readablemedium” as used herein includes any medium that participates inproviding instructions to processor 112 or other components of computersystem 100 for execution. Such a medium may take many forms including,but not limited to, non-volatile media, volatile media, and transmissionmedia. Common forms of non-volatile media include, for example, a floppydisk, a flexible disk, a hard disk, magnetic tape or any other magneticmedium, a compact disc ROM (CD-ROM) or any other optical medium, punchcards or any other physical medium with patterns of holes, aprogrammable ROM (PROM), an erasable PROM (EPROM), electrically EPROM(EEPROM), a flash memory, any other memory chip or cartridge, or anyother medium from which computer system 100 can read and which issuitable for storing instructions. In the present embodiment, an exampleof a non-volatile medium is mass storage device 118 which as depicted isan internal component of computer system 100, but will be understood toalso be provided by an external device. Volatile media include dynamicmemory such as RAM 114. Transmission media include coaxial cables,copper wire or fiber optics, including the wires that comprise bus 122.Transmission media can also take the form of acoustic or light waves,such as those generated during radio frequency or infrared datacommunications.

Moreover, the present invention may be downloaded as a computer programproduct, wherein the program instructions may be transferred from aremote virtual resource, such as a virtual resource 160, to requestingcomputer system 100 by way of data signals embodied in a carrier wave orother propagation medium via a network link 134 (e.g. a modem or networkconnection) to a communications interface 132 coupled to bus 122.Virtual resource 160 may include a virtual representation of theresources accessible from a single system or systems, wherein multiplesystems may each be considered discrete sets of resources operating onindependent platforms, but coordinated as a virtual resource by a gridmanager. Communications interface 132 provides a two-way datacommunications coupling to network link 134 that may be connected, forexample, to a local area network (LAN), wide area network (WAN), or anInternet Service Provider (ISP) that provide access to network 102. Inparticular, network link 134 may provide wired and/or wireless networkcommunications to one or more networks, such as network 102, throughwhich use of virtual resources, such as virtual resource 160, isaccessible as provided within a grid environment 150. Grid environment150 may be part of multiple types of networks, including a peer-to-peernetwork, or may be part of a single computer system, such as computersystem 100.

As one example, network 102 may refer to the worldwide collection ofnetworks and gateways that use a particular protocol, such asTransmission Control Protocol (TCP) and Internet Protocol (IP), tocommunicate with one another. Network 102 uses electrical,electromagnetic, or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 134and through communication interface 132, which carry the digital data toand from computer system 100, are exemplary forms of carrier wavestransporting the information. It will be understood that alternate typesof networks, combinations of networks, and infrastructures of networksmay be implemented.

When implemented as a server system, computer system 100 typicallyincludes multiple communication interfaces accessible via multipleperipheral component interconnect (PCI) bus bridges connected to aninput/output controller. In this manner, computer system 100 allowsconnections to multiple network computers.

Additionally, although not depicted, multiple peripheral components andinternal/external devices may be added to computer system 100, connectedto multiple controllers, adapters, and expansion slots coupled to one ofthe multiple levels of bus 122. For example, a display device, audiodevice, keyboard, or cursor control device may be added as a peripheralcomponent.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 1 may vary. Furthermore, those of ordinary skill in theart will appreciate that the depicted example is not meant to implyarchitectural limitations with respect to the present invention.

With reference now to FIG. 2, a block diagram illustrates one embodimentof the general types of components within a grid environment. In thepresent example, the components of a grid environment 150 include aclient system 200 interfacing with a grid management system 240 whichinterfaces with server clusters 222, servers 224, workstations anddesktops 226, data storage systems 228, and networks 230. For purposesof illustration, the network locations and types of networks connectingthe components within grid environment 150 are not depicted. It will beunderstood, however, that the components within grid environment 150 mayreside atop a network infrastructure architecture that may beimplemented with multiple types of networks overlapping one another.Network infrastructure may range from multiple large enterprise systemsto a peer-to-peer system to a single computer system. Further, it willbe understood that the components within grid environment 150 are merelyrepresentations of the types of components within a grid environment. Agrid environment may simply be encompassed in a single computer systemor may encompass multiple enterprises of systems. In addition, it willbe understood that a grid vendor may provide grid environment 150, wherethe grid vendor may calculate a cost for use of resources within gridenvironment 150 based on the amount of time required for a grid job toexecute or the actual amount of resources used, for example.

The central goal of a grid environment, such as grid environment 150 isorganization and delivery of resources from multiple discrete systemsviewed as virtual resource 160. Client system 200, server clusters 222,servers 224, workstations and desktops 226, data storage systems 228,networks 230 and the systems creating grid management system 240 may beheterogeneous and regionally distributed with independent managementsystems, but enabled to exchange information, resources, and servicesthrough a grid infrastructure enabled by grid management system 240.Further, server clusters 222, servers 224, workstations and desktops226, data storage systems 228, and networks 230 may be geographicallydistributed across countries and continents or locally accessible to oneanother. It will be understood that mechanisms for discovery of gridresources within virtual resource 160 are not depicted herein, however,client system 200 may discover the resources within virtual resource 160as advertised from local and global directories available within gridenvironment 150.

In the example, client system 200 interfaces with grid management system240. Client system 200 may represent any computing system sendingrequests to grid management system 240. In particular, client system 200may send virtual job requests and jobs to grid management system 240 andgrid management system 240 may respond with a grid offer and controlsprocessing of grid jobs. Further, while in the present embodiment clientsystem 200 is depicted as accessing grid environment 150 with a request,in alternate embodiments client system 200 may also operate within gridenvironment 150.

While the systems within virtual resource 160 are depicted in parallel,in reality, the systems may be part of a hierarchy of systems where somesystems within virtual resource 160 may be local to client system 200,while other systems require access to external networks. Additionally,it is important to note, that client system 200 may physically encompassthe systems depicted within virtual resources 160. Further, the systemsin virtual resource 160 may be allocated among resource nodes andexecution environments, where a resource node is a grouping of resourcesenabled to perform a particular grid function and an executionenvironment is a grouping of resources and resource nodes enabled tohandle a particular grid job.

To implement grid environment 150, grid management system 240facilitates grid services. Grid services may be designed according tomultiple architectures, including, but not limited to, the Open GridServices Architecture (OGSA). In particular, grid management system 240refers to the management environment which creates a grid by linkingcomputing systems into a heterogeneous network environment characterizedby sharing of resources through grid services.

In one example, as will be further described in detail, grid managementsystem 240 may include a grid service that allocates resources andresource nodes to an execution environment suitable for an incoming gridjob and manages resources and resource nodes within the executionenvironment to ensure the performance of the grid job. In addition, gridmanagement system may include a grid service that first tests andverifies grid resources allocated to an execution environment before agrid job is routed to the allocated resources. In the event that anerror is detected, the grid service will attempt to resolve the error orreplace the resource.

Referring now to FIG. 3, a block diagram illustrates one example of anarchitecture that may be implemented in a grid environment. As depicted,an architecture 300 includes multiple layers of functionality. As willbe further described, the present invention is a process which may beimplemented in one or more layers of an architecture, such asarchitecture 300, which is implemented in a grid environment, such asthe grid environment described in FIG. 2. It is important to note thatarchitecture 300 is just one example of an architecture that may beimplemented in a grid environment and in which the present invention maybe implemented. Further, it is important to note that multiplearchitectures may be implemented within a grid environment.

Within the layers of architecture 300, first, a physical and logicalresources layer 330 organizes the resources of the systems in the grid.Physical resources include, but are not limited to, servers, storagemedia, and networks. The logical resources virtualize and aggregate thephysical layer into usable resources such as operating systems,processing power, memory, I/O processing, file systems, databasemanagers, directories, memory managers, and other resources.

Next, a web services layer 320 provides an interface between gridservices 310 and physical and logical resources 330. Web services layer320 implements service interfaces including, but not limited to, WebServices Description Language (WSDL), Simple Object Access Protocol(SOAP), and eXtensible mark-up language (XML) executing atop an InternetProtocol (IP) or other network transport layer. Further, the Open GridServices Infrastructure (OSGI) standard 322 builds on top of current webservices 320 by extending web services 320 to provide capabilities fordynamic and manageable Web services required to model the resources ofthe grid. In particular, by implementing OGSI standard 322 with webservices 320, grid services 310 designed using OGSA are interoperable.In alternate embodiments, other infrastructures or additionalinfrastructures may be implemented a top web services layer 320.

Grid services layer 310 includes multiple services which may beincorporated into grid management system 240. For example, grid serviceslayer 310 may include grid services designed using OGSA, such that auniform standard is implemented in creating grid services.Alternatively, grid services may be designed under multiplearchitectures. Grid services can be grouped into four main functions. Itwill be understood, however, that other functions may be performed bygrid services.

First, a resource management service 302 manages the use of the physicaland logical resources. Resources may include, but are not limited to,processing resources, memory resources, and storage resources.Management of these resources includes scheduling jobs, distributingjobs, and managing the retrieval of the results for jobs. Resourcemanagement service 302 monitors resource loads and distributes jobs toless busy parts of the grid to balance resource loads and absorbunexpected peaks of activity. In particular, a user may specifypreferred performance levels so that resource management service 302distributes jobs to maintain the preferred performance levels within thegrid.

Second, information services 304 manages the information transfer andcommunication between computing systems within the grid. Since multiplecommunication protocols may be implemented, information services 304manages communications across multiple networks utilizing multiple typesof communication protocols.

Third, a data management service 306 manages data transfer and storagewithin the grid. In particular, data management service 306 may movedata to nodes within the grid where a job requiring the data willexecute. A particular type of transfer protocol, such as Grid FileTransfer Protocol (GridFTP), may be implemented.

Finally, a security service 308 applies a security protocol for securityat the connection layers of each of the systems operating within thegrid. Security service 308 may implement security protocols, such asOpen Secure Socket Layers (SSL), to provide secure transmissions.Further, security service 308 may provide a single sign-on mechanism, sothat once a user is authenticated, a proxy certificate is created andused when performing actions within the grid for the user.

Multiple services may work together to provide several key functions ofa grid computing system. In a first example, computational tasks aredistributed within a grid. Data management service 306 may divide up acomputation task into separate grid services requests of packets of datathat are then distributed by and managed by resource management service302. The results are collected and consolidated by data managementsystem 306. In a second example, the storage resources across multiplecomputing systems in the grid are viewed as a single virtual datastorage system managed by data management service 306 and monitored byresource management service 302.

An applications layer 340 includes applications that use one or more ofthe grid services available in grid services layer 310. Advantageously,applications interface with the physical and logical resources 330 viagrid services layer 310 and web services 320, such that multipleheterogeneous systems can interact and interoperate.

With reference now to FIG. 4, there is depicted a block diagram of aninstance of a grid management system managing multiple executionenvironments within a grid environment in accordance with the method,system, and program of the present invention. As depicted, gridmanagement system (GMS) 240 manages multiple execution environments 402and 410. In the example, each of execution environments 402 and 410include multiple resources allocated for handling a particular grid jobor batch of grid jobs. It will be understood that GMS 240 may physicallyinclude multiple instances that provide the functions of GMS 240. Inaddition, GMS 240 may be distributed across multiple physical systemswithin grid environment 150 and may incorporate multiple grid services.

According to one embodiment, GMS 240 builds execution environments ofgrid resources that are able to handle grid jobs and provide aparticular level of quality of service for grid jobs. GMS 240 may buildan execution environment of all new resources, where a new resource isone that has not previously been included in a particular executionenvironment. In addition, GMS 240 may build an execution environment andthen add new resources as additional resources are required or as faultyresources requirement replacement. Additionally, GMS 240 may reuse anexecution environment for multiple grid jobs from multiple disparateclients, as long as the execution environment meets the specificationsagreed to for the performance and other requirements of each grid job.

Within an execution environment, each resource may be controlled by alocal management system that interfaces with GMS 240 via the gridinfrastructure. In addition, within an execution environment, groups ofresources may be controlled by a hardware level management system, suchas a cluster based management system that manages the load acrossmultiple server systems grouped in a cluster. It will be understood thatadditional configurations of resources, in additional to theconfigurations depicted for purposes of example, may implement thepresent invention.

In one example, execution environment 402 includes multiple gridresources, which when viewed individually, include a hardware platform404, a network adapter 406, and operating system software 408. Theseindividual resources may be distributed among multiple physicallydisparate locations. Further, these individual resources may be part ofclusters of server systems managed by cluster management tools.

GMS 240 may also manage an execution environment 410. Executionenvironment 410 includes hardware platform 412, network adapter 414, andoperating system software 416. In addition, GMS 240 moves hardwareplatform 404 from execution environment 402 to execution environment410.

To illustrate an advantage of the invention, when GMS 240 allocateshardware platform 404 to execution environment 410, hardware platform404 is considered a new resource which needs to be verified forfunctionality before allowing any grid jobs routed to executionenvironment 410 to execute on hardware platform 404. In one example, GMS240 calls a hardware testing diagnostic tool 430 of operating systemsoftware 416 to request that hardware testing diagnostic tool 430perform diagnostic testing of the functionality of hardware platform404. Additionally, an operating system resource executing on hardwareplatform 404 may be called to perform the diagnostic testing. Hardwaretesting diagnostic tool 430 may return a log file indicating any errorsfoiled during the testing. In another example, GMS 240 may direct testequations or test operations to hardware platform 404 and receive testresults which can be compared with expected results to determine ifthere are any functionality errors. If a functionality error isdetected, then GMS 240 may remove the new resource and attempt toreplace the resource within execution environment 410.

In the example, hardware testing diagnostic tool 430 is depicted as anexample of a local or native diagnostic tool that can be called toperform functionality testing at the resource level, rather than from atest job performed by GMS 240. It will be understood that each type ofresource may include a local, native, or on-board diagnostic tool orcommands that can be called to perform functionality testing at theresource level. In addition, it will be understood that operatingsystems or application software may include diagnostic tools or commandthat can be called to perform functionality testing of other resourcesat the resource level.

Referring now to FIG. 5, there is depicted a block diagram of a gridmanagement system for managing a grid environment in accordance with themethod, system, and program of the present invention. In the example,GMS 240 includes multiple grid modules that provide grid services andstore data for access across grid environment 150. It is important tonote that the grid modules described in GMS 240 may be distributed amongmultiple grid managers within grid environment 150 and may interact withresource level management tools.

As depicted, GMS 240 includes a grid scheduler 501 for detectingincoming jobs and scheduling execution of incoming jobs within gridenvironment 150. In particular, when grid scheduler 501 detects anincoming grid job, grid scheduler 501 passes the incoming grid job to agrid allocation service 502.

Grid allocation service 502 controls the allocation of resources withinexecution environments. Grid allocation service 502 may maintainavailable execution environments, may move resources among executionenvironments, and may build new execution environments. In oneembodiment, grid allocation service 502 may build resource nodes ofresources required to support a type of job and then move entireresource nodes among execution environments. For example, gridallocation service 502 may build a resource node with the hardwareplatform, operating system resources, network connector resources,storage subsystems, and application software required to supportdatabase based jobs. In addition, grid allocation service 502 maycommunicate with grid management systems for other grid environments tocontrol access of additional resources from external grid environments.

When grid allocation service 502 allocates a new resource within anexecution environment, grid allocation service 502 may call gridverification service 506 before enabling job router 504 to route a gridjob to the new resource. In another embodiment, grid allocation service502 may call grid verification service 506 to test a resource at thecompletion of a current grid job, but prior to allocating the newresource to a new execution environment. Further, in another embodiment,grid verification service 506 may continue to test and verify a resourceafter a grid job begins in the execution environment, and in particular,may test a verify the resource using client provided testing criteria.

Grid verification service 506 determines what tests should be run on thenew resource to verify functionality, runs the tests on the newresource, and analyzes the test results. Grid verification service 506returns a report to grid allocation service 502 either indicating theverified functionality of the new resource or indicating the unresolvederror condition within the new resource.

According to one embodiment, if grid verification service 506 detects anerror in the functionality of a new resource, grid verification service506 calls grid degradation prevention service 508 with a request forerror resolution. Grid degradation prevention service 508 may attempt toresolve the error in the new resource by communicating with errorresolution tools local to the new resource or by performing errorresolution routines. In one example, if grid verification service 508detects that the average utilization of a CPU is greater than 90%, thengrid verification service 508 may call grid degradation preventionservice 508 because CPU average CPU utilization of more than 90% isconsidered an error. Grid degradation prevention service 508 may thenenable another CPU or activate another logical partition to preventfurther deterioration of the performance.

It addition to performing tests to detect errors, grid verificationservice 506 may receive error indicators from grid error monitoringservice 510. Grid error monitoring service 510 monitors each executionenvironment within grid environment 150 for conditions which mayindicate errors in the environment. The errors reported by grid errormonitoring service 510 may be in the form of error messages or errorlogs. In one example, grid error monitoring service 510 may detect andreport errors in a manner similar to the grid error monitoring servicedescribed in co-pending U.S. patent application Ser. No. 11/031,051,herein incorporated by reference.

It will be understood that although the services described hereinprovide automated processing for a grid job, any of the grid servicesdescribed as part of grid management system 240 may be performed by asystem administrator through human intervention. In addition, it will beunderstood that grid management system 240 may include additional gridservices, job queues, and storage systems for improving the efficiencyof grid environment 150 overall and the efficiency of grid managementsystem 240 in handling individual grid jobs.

With reference now to FIG. 6, there is depicted a block diagram ofexamples of components of a grid verification service in accordance withthe method, system, and program of the present invention. Asillustrated, grid verification service 506 includes a testing controller602. Testing controller 602 is initiated when a new resource is added toan execution environment. In addition, it will be understood thattesting controller 602 may be initiated responsive to other eventswithin the grid environment.

When testing controller 602 is initiated, testing controller 602searches available test table 604 for applicable tests for the newresource. As will be further described with reference to FIG. 7,available test table 604 includes tests according to type of resourceand further specified by class of resource. In addition, available testtable 604 includes both tests that call local resource tests and testjobs to be run by testing controller 602. In addition to accessingavailable test table 604, testing controller 602 may query new resourcesto determine if the resource includes a local diagnostic tool that canbe called to allow the new resource to self-verify.

Testing controller 602 collects test results in a test results table606. Test results table 606 may include both log file data and directtesting results, organized according to new resource.

Once testing controller 602 completes testing of a new resource, errordetector 610 analyzes test results table 606 for errors. In particular,error detector 610 may search log files for error conditions. Inaddition, error detector 610 may compare test results from testsperformed by testing controller 602 with expected results and detecterrors where results do not match expectations.

Then, error detector 610 accesses acceptable errors table 608 whendetermining how to respond to detected errors. Acceptable errors table608 includes conditions for errors that are acceptable within aparticular execution environment or within the grid environment. Forexample, a log file for a tested disk subsystem may indicate thereallocation of bad blocks, however, reallocation of bad blocks on adisk subsystem is designated in acceptable errors table 608 as a normalfunction of disk controllers.

Error detector 610 may call grid degradation prevention service 508 witha request for grid degradation prevention service 508 to attempt toresolve detected errors. In one example, grid degradation preventionservice 508 is able to resolve a detected error and returns the errorresolution report to error detector 610. In another example, griddegradation prevention service 508 is not able to resolve a detectederror and returns an indicator that the error was not resolved. Errordetector 610 then informs grid allocation service 502 whether there areany unresolved errors or whether all new resources are verified.

Referring now to FIG. 7, there is depicted an illustrative example ofentries in a test availability table in accordance with the method,system, and program of the present invention. As depicted, availabletest table 604 includes tests specified according to the general type ofresource and further specified according to a class of resources withinthe type. In addition, tests may be specified for each particularresource by resource name. It will be understood that the tests depictedin available test table 604 are examples of the types of tests that maybe performed and called, and that the actual test sequences may beadjusted according to the precision of testing required to validate thefunctionality of a grid resource.

When a resource is a processor, available test table 604 designatesmultiple available tests and the expected result types, as illustratedat reference numeral 702. In a first example, a processor may be testedby calling the native processor diagnostics that can be invoked from anoperating system; available test table 604 may include the callreferences for multiple types of operating system based processordiagnostics. The native processor diagnostics may return a log file. Ina second example, a processor may be tested by running a test job with aset of test equations and collecting test results. Multiple sets of testequations may be available and specified according to the type ofprocessor or processors. In either example, processors, including thebus and backplanes may be tested and the results verified.

When a resource is memory, available test table 604 designates multipleavailable tests and the expected result types, as illustrated atreference numeral 704. In a first example, memory may be tested bycalling a local operating system based memory diagnostics tool;available test table 604 may include the command references for multipletypes of operating system based memory diagnostics. In a second example,memory may be tested by running a test job of a bit check test on thememory; test results are collected for comparison against an anticipatedbit pattern. In a third example, memory may be tested by running a testjob of a full pattern read and write test designed to verify the memoryfunctions; test results are collected for determination whether the readand write were properly executed. In one example, testing controller 602may select the full pattern read and write test for faster memoryresources and the bit check test for slower memory resources.

When a resource is a network adapter, available test table 604 makesmultiple tests are available and sorted by the class of network adapter,as illustrated at reference numeral 706. Classes of network adapters mayinclude, but are not limited to, SAN adapters and IP adapters. For eachclass of network adapter, a series of tests may be performed. First, inthe series, testing controller 602 is directed to call an on-boardloop-back test. In particular, a network adapter may include on-boarddiagnostics that can be invoked by other systems through a command call.Second, in the series, testing controller 602, is directed to run aconnectivity test. In one example, a connectivity test such as a pingtest may be used, where a resulting “ping” is expected. It will beunderstood that additional tests may be specified to test thefunctionality of both individual network adapters and classes of networkadapters.

When a resource is a device controller, such as a SCSI devicecontroller, available test table 604 makes multiple tests available andstored by class of device controller, as illustrated at referencenumeral 708. For each class of device controller, a series of tests maybe performed. First, in the series, testing controller 602 is directedto call an on-board loop back test to test the local hardware. Second,in the series, testing controller 602 is directed to perform test job ofa test access of the hardware. A test access, in general, includesinstructions that enable verification of the adapters, paths, and readand write capabilities of a device controller. For example, if thedevice controller is a disk subsystem, the test access may includeinstructions to write a file on each disk with a predetermined datapattern, read back each file, and then delete each file.

When a resource is a storage subsystem, such as a disk or tape,available test table 604 makes multiple tests available and stored byclass of storage subsystem, as illustrated at reference numeral 710. Foreach class of storage subsystem, a particular test access may beperformed. In a case where the media is not removeable, the test mayinclude instructions to verify each part of the storage subsystem.Alternatively, in a case where the media is removeable, the test mayinclude instructions to verify the paths and read and write capabilitiesof the whole storage subsystem. Further, if a storage subsystem includesan on-board diagnostic tool, available test table 604 may include a calloperation for the on-board diagnostic tool.

When a resource is operating system software, available test table 604makes multiple tests available according to type of operating system, asillustrated at reference numeral 712. For each type of operating system,the test includes instructions to call the operating system tools forparameter testing and readiness testing. In particular, each operatingsystem may include diagnostic tools that can be called to verify theoperating system. In one example, the test may include instructions tocall tools within the AIX operating system (AIX is a registeredtrademark of International Business Machines Corporation). Inparticular, with reference to the AIX operating system, a “lppchk-v”instruction can be called to test to ensure that no software componentsinconsistencies exist; a “oslevel-r” instruction can be called torequest the operating system release level and maintenance level; a“instfix-ik” instruction can be called to verify that all filesets arepresent for the current release and maintenance level; a “lslpp-L”instruction can be called, and used with a filter that specifies whichresults are requested to determine the presence and state of anyspecific operating system file set or device driver; and a “set”instruction can be called, and used with a filter, to determine thepresence and value of required environment variables. It will beunderstood that additional AIX operating system instructions may becalled to test the parameters and readiness of the AIX operating system.In addition, it will be understood that other types of instructions maybe specified to call for other operating systems.

When a resource is application software, available test table 604 makesmultiple tests available according to the type of software, asillustrated at reference numeral 714. If application software includes aself-verification routine, available test table 604 may include aspecific call for the self-verification routine. Alternatively,available test table 604 may include an instruction to run afunctionality test job for the particular class of application of thecurrent application. In one example, the application software resourceis DB2 database software (DB2 is a registered trademark of InternationalBusiness Machines Corporation), which is in the database software class.A database class functional test job would require performance of thefollowing operations: (1) verify the correct daemons and processes arerunning; (2) connect to the database and verify connection to thedatabase; (3) create a test table in the database; (4) populate testdata into the table; (5) execute a query with known results against thetable and verify the results; (6) delete the test table; (7) disconnectfrom the database; and (8) remove the database alias. It will beunderstood that additional operations that test and verify databasesoftware may be invoked. In addition, it will be understood thatavailable test table 604 illustrates sample test cases with results andresult types, however, those skilled in the art could extend thesesample test cases to additional or more suitable platforms andapplications.

With reference now to FIG. 8, there is depicted is a high level logicflowchart of a process and program for controlling grid job routing toverified resources within an execution environment for the grid job inaccordance with the method, system, and program of the presentinvention. As illustrated, the process starts at block 800 andthereafter proceeds to block 802. Block 802 depicts a grid schedulerreceiving a new grid job. Next, block 804 depicts grid schedulerinforming the grid allocation service about the new grid job.Thereafter, block 806 depicts the grid allocation service assembling theresources required for the new grid job into an execution environmentfor the new grid job. Next, block 808 depicts the grid allocationservice initiating the grid verification service to verify the newresources in the execution environment, and the process passes to block810.

Block 810 depicts a determination whether the grid allocation servicereceives an indicator that the resource functionality is verified. Ifthe resource functionality is verified, then the process passes to block812. Block 812 depicts the grid allocation service informing the gridjob router to route the job to the resources or a replacement resourcewithin the execution environment, and the process ends. Otherwise, atblock 810, if resource functionality is not verified, then the processpasses to block 814. Block 814 depicts the grid allocation servicelocation replacement resources and replacing non-functional resourceswithin the execution environment; then the process returns to block 808.

Referring now to FIG. 9, there is depicted a high level logic flowchartof a process and program for controlling resource verification forresources added to an execution environment for a grid job prior to gridjob submission to the resources in accordance with the method, system,and program of the present invention. As illustrated, the process startsat block 900 and thereafter proceeds to block 902. Block 902 depicts adetermination whether the grid verification service receives a requestto verify new resources from the grid allocation service. If a requestto verify new resources is received, then the process passes to block904. Block 904 depicts selecting tests required for the new resourcesfrom a test availability table. Next, block 906 depicts running theselected tests on the new resources, and the process passes to block908.

Block 908 depicts collecting the test results in a test results tablefor each new resource. Block 910 depicts a determination whether resultsare received in response to all run tests. If all results are not yetreceived, then the process returns to block 908. Once all results arereceived, then the process passes to block 912.

Block 912 depicts a determination whether any errors are detected in theresults. If errors are not detected, then the process passes to block920. Block 920 depicts informing the grid allocation service that theresource functionality is verified, and the process ends. Otherwise, atblock 918, if errors are detected, then the process passes to block 916.

Block 916 depicts submitting the error to the resource degradationprevention service. The resource degradation prevention service attemptsto resolve the error. If the resource degradation prevention servicecannot resolve the error, then the process passes to block 922. Block922 depicts informing the grid allocation service about the resourceerror, and the process ends. Otherwise, at block 918, if the resourcedegradation prevention service can resolve the error, then the processpasses to block 920.

While the invention has been particularly shown and described withreference to a preferred embodiment, it will be understood by thoseskilled in the art that various changes in form and detail may be madetherein without departing from the spirit and scope of the invention.

1. A computer-implemented method for verifying a resource within aparticular execution environment for a grid job submitted in a gridenvironment, comprising: enabling a grid environment comprising aplurality of computing systems each comprising at least one resource andcommunicatively connected over a network layer through a grid managementsystem to share each said at least one resource through at least one webservice layer atop at least one grid service layer implemented within anopen grid services architecture, wherein said at least one grid servicelayer comprises a grid allocation service and a grid verificationservice; managing, by said grid allocation service, allocation of aplurality of execution environments each comprising a separate selectionof said at least one resource comprising a grouping of at least onehardware platform, at least one network adapter, and at least one typeof operating system software; distributing, by said grid allocationservice, a grid job to a particular execution environment from amongsaid plurality of execution environments comprising a particulargrouping of said at least one resource for handling said grid job;responsive to said grid allocation service allocating a new hardwareplatform to said particular execution environment from among saidplurality of execution environments to replace a defective hardwareplatform within said particular execution environment, triggering a gridverification service of said grid management system to determine atleast one functionality test for running on said new hardware platformfrom a plurality of functionality tests specified according to a type ofresource, a class of resource, and at least one expected result;running, by said grid verification service, said at least onefunctionality test on said new hardware platform as controlled by saidgrid management system by performing at least one of sending a testequation to said particular execution environment and calling adiagnostic tool of a particular operating system software running withinsaid particular execution environment enabled to locally test said newhardware platform; responsive to said grid verification servicereceiving a result comprising at least one of a result from said testequation and a log file from said diagnostic tool indicating at leastone test result, analyzing by said grid verification service said resultfor a plurality of specified error conditions specified in a particularexpected result; responsive to said grid verification service detectingat least one error from among said plurality of specified errorconditions, attempting by said grid verification service to resolve saidat least one error; responsive to said grid verification serviceresolving said error, verifying whether said result meets an expectedresult before enabling routing of said grid job to said new hardwareplatform, such that a functionality of said new hardware platform isautomatically verified before access to said new hardware platform isallowed; responsive to said error remaining unresolved, replacing, bysaid grid allocation service, said new hardware platform in saidparticular execution environment.
 2. The computer-implemented method ofclaim 1 wherein triggering a grid verification service of said gridmanagement system to determine at least one functionality test forrunning on said new hardware platform from a plurality of functionalitytests specified according to a type of resource, a class of resource,and at least one expected result, further comprises: selecting, by saidgrid verification system, said at least one functionality testcomprising a plurality of test equations specified for a particular typeof processor within said particular execution environment from among aplurality of processor types and said particular expected result.
 3. Thecomputer-implemented method of claim 1 wherein triggering a gridverification service of said grid management system to determine atleast one functionality test for running on said new hardware platformfrom a plurality of functionality tests specified according to a type ofresource, a class of resource, and at least one expected result, furthercomprises: selecting, by said grid verification system, said at leastone functionality test comprising a command reference for a memorydiagnostic tool specified for said particular operating system softwarefrom among a plurality of type of operating system software to locallyrun on a memory resource within said particular execution environmentand a particular bit patterns for said particular expected result. 4.The computer-implemented method of claim 1 wherein triggering a gridverification service of said grid management system to determine atleast one functionality test for running on said new hardware platformfrom a plurality of functionality tests specified according to a type ofresource, a class of resource, and at least one expected result, furthercomprises: selecting, by said grid verification system, said at leastone functionality test comprising said test equation of a full patternread and write test for verifying a functionality of a memory resourcewithin said particular execution environment and said particularexpected result.
 5. The computer-implemented method of claim 1 whereintriggering a grid verification service of said grid management system todetermine at least one functionality test for running on said newhardware platform from a plurality of functionality tests specifiedaccording to a type of resource, a class of resource, and at least oneexpected result, further comprises: selecting, by said grid verificationsystem, said at least one functionality test comprising said testequation of a plurality of instructions for verifying a plurality ofpaths and read and write capabilities of a storage resource within saidparticular execution environment and said particular expected result.